Description of your changes

This PR introduces the possibility for customers to set the Logger level at runtime as well as retrieving the current level both in string (i.e. DEBUG) and numeric (i.e. 8) notations.

Before this PR, customers could only set the log level when creating a new Logger instance. There are however use cases (see #1265) in which customers might want to change the log level of an existing Logger instance at runtime. Likewise, customers were also not able to get the current log level as its value was treated as internal by the utility.

The PR introduces two new methods and a public property to the Logger class:

Get current log level

The first method added is getLevelName(), this method returns the current log level as string:

import { Logger } from '@aws-lambda-powertools/logger';

const logger = new Logger();

logger.getLevelName(); // returns "INFO"

Get current log level number value

The second change is a new public class property called level, which returns the numeric value of the current log level:

import { Logger } from '@aws-lambda-powertools/logger';

const logger = new Logger();

logger.level; // returns 12

Set a new log level

The third one is a new setLogLevel() method. This method accepts a string (both lower and uppercase) and sets the corresponding log level.

import { Logger } from '@aws-lambda-powertools/logger';

const logger = new Logger();

logger.setLogLevel('DEBUG');

If an invalid value is passed, the method will throw an error.

In order to support these methods and streamline the log level handling the PR also changes the Logger class to exclusively use numeric values internally. This, together with the changes above, aligns the Logger utility to the behavior found in the Python version of Powertools for AWS.

Finally, the PR changes the access modifier of the shouldPrint method from private to protected, so that customers can optionally extend the method when subclassing the Logger instance and implement custom logging decision logic (#1307 (comment)).

The PR also covers a couple of housekeeping items:

• Replace Math.random with randomInt from node:crypto in log sampling decision
• Added @deprecated notice to createLogger helper that informs of the function's deprecation in the next major release

Related issues, RFCs

Issue number: #1265

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.